-
Notifications
You must be signed in to change notification settings - Fork 8
Issue Template config #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
We can also point folks to the Node slack or other places with active q/a |
Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com>
|
@jonchurch anything holding this up or can we merge this? |
UlisesGascon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hold it please! I will replace the link when the security policy is updated (STF part)
|
We got the email setup today. Which PR were we pending on this so I can make sure to drop the new reporting email in? |
| contact_links: | ||
| - name: Security Report | ||
| url: https://expressjs.com/en/resources/contributing.html#security-policies-and-procedures | ||
| about: Email security reports to the maintainer list serve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

This draft PR introduces a
config.yml. See Github docs here.As is, this PR does two things:
blank_issues_enabled: false)Everything about this config is up for debate. Currently the linked page doesn't clearly state an email address, which is something we can address elsewhere.